JBoss.orgCommunity Documentation

Chapter 4. Mobicents SIP Presence Server

4.1. Functional Architecture of the SIP Presence Server
4.2. Configuring The SIP Presence Server
4.2.1. Configuring the Abstract SIP Event Publication Interface
4.2.2. Configuring the Abstract SIP Event Subscription Interface
4.2.3. Configuring the Concrete SIP Event Interfaces

The Mobicents SIP Presence Server is a free and open source implementation of a SIP Presence Server, as defined by the Internet Engineering Task Force (IETF), the Open Mobile Alliance (OMA), the 3rd Generation Partnership Project (3GPP) and the European Telecommunications Standards Institute (ETSI).

The SIP Presence Server is an entity that accepts, stores and distributes SIP presence information.

The SIP Presence Server is comprised of the following functional elements:

Presence Publication Control

This functional element manages the publication of presence events, which includes not only the handling of new publications, but also the refreshing, modification or removal of, already-published information.

Because the presence resource, which is also called a presentity, can have multiple publications simultaneously, such as some state published by a user agent or device, and some location data published by a Presence Network Agent (on behalf of the presentity), this element is also responsible for composing all of the different publications for the same resource.

In some presence networks, it may be of interest to allow resources to have a static presence state which is stored in the XDM Server. In cases like these, Presence Publication Control may need to interface with the XDM Server to retrieve and subscribe to (learn about changes to) that information, and use it when composing the final presence information document.

Presence Subscription Control

This functional element handles subscriptions to presence events or to the list of subscribers (watchers), for any specific resource. It is, of course, responsible for emitting notifications related to those subscriptions.

Presence authorization rules, which define if a subscription is allowed or rejected and, if allowed, define which transformations to the original presence events are needed, are stored on the XDM Server by the user. Thus, Presence Subscription Control needs to retrieve and subscribe to that information.

Presence Rules Cache

This element is responsible for interfacing with the XDM Server that manages the user's XML presence rules documents. It is responsible for providing the presence rules to the Presence Subscription Control, which are used to authorize the subscriptions it handles.

The implementation architecture of the SIP Presence Server also contains client-side components:

Several features of the SIP Presence Server are configurable, through XML files or JMX.: